Generating JCL

After you create and configure a SequeLink Server for the first time, you must generate JCL to complete the configuration task. The SequeLink Manager customizes JCL obtained from the SequeLink_HLQ.SKELS data set and saves the customized output in a data set named USR_HLQ.Servername.CNTL. Both SequeLink_HLQ and USR_HLQ are passed to the SSMC clist when you start the SequeLink Manager for z/OS.

See "Data Sets Created During Installation" for a description of SequeLink_HLQ and USR_HLQ.

Generating JCL allows you to easily keep the JCL members synchronized with the actual server configuration.

JCL Members

The following list shows the JCL members that are generated and the tasks they perform. Also, this list notes any tasks you must perform for the JCL member.

BINDxx: These members bind all required SequeLink packages and plans for your DB2 subsystems. Read the comments in this bind job carefully. The tailored job contains a job-step for the defined DB2 interface and bind statements for all data sources that use this interface.
BIND7: bind job for DB2 v7
BIND8C: bind job for DB2 v8, compatibility mode
BIND8N: bind job for DB2 v8, new function mode
BIND9: bind job for all DB2 v9 modes.

NOTE: If data sources are added later, an interface is changed, or the collection-prefixes of a data source are changed, you must regenerate and submit these members.

CFGPRINT: A summary member you can use for debugging purposes that reports the content of all variables at the time of JCL generation. This member also lists the user and date and time of the last JCL generation.
EVLDEF: This member creates the event trace file for the server.
INIT: This member contains operator interface commands that will be executed after the successful startup of the server.

NOTE: To add or delete operator interface commands you want to execute after the successful startup of the server, edit this member.

RUNSMF: This member is a sample job that allows SMF records to be printed.
RUNSRVR: This member is the started task or job that is used to start the server.

NOTE: If the DB2 interface is changed, you must regenerate this member, and restart the server.

RUNCLUST: This member prints out the Sysplex registration information.
RUNWHAT: This member is a diagnostic job that prints all versions of the software components and can be used for debugging. Execute this job only on a specific request from DataDirect Technologies technical support.

Generating the JCL

To generate JCL:

Type G beside the SequeLink Server on the ServerList panel; then, press ENTER. The JCL Settings panel appears.





If you want to change the default settings used for JCL generation, provide the following information:

Job prefix: Type the name of the site-specific job name.

Job Class: Type the name of the site-specific job class.

Output Class: Type the name of the site-specific output class.

Accounting Info: Type your site-specific jobcard account information.

Choose whether to generate the JCL for the server as a started task (highly recommended) or as a normal job:
Type 1 to generate the JCL for the server as a started task; then, press ENTER.
Type 2 to generate the JCL for the server as a normal job; then, press ENTER.

Data Sets Created During Installation

In previous versions of SequeLink Server for DB2 on z/OS, both the SequeLink installation datasets and the specific SequeLink Server datasets used a high-level qualifier (HLQ) prefix.

This naming convention has been changed to give the SequeLink administrator more control and flexibility over this dataset naming convention:

Deployment, for example, from development to production, is easier.
SequeLink Installation libraries are read-only.
Multiple Server environments, such as Production, Development, and Quality Assurance, can be administered separately. For example:
User-specific dataset names can be made unique for each environment
The datasets can be allocated on separate volumes.
RACF dataset security can be set for each environment.

Two new dataset prefixes have been introduced:

HLQ is the installation dataset prefix. The HLQ prefix is required at install time.
USR is the server-specific dataset prefix. The USR prefix and the server name (USR.servername) are required when a SequeLink Server is added.

The maximum length for each qualifier is 24 characters; the name must be compliant with the operating system dataset naming convention.

The installation libraries are copied to datasets prefixed with the installation data set prefix (HLQ). The SequeLink servers generated and configured with the SequeLink Server Manager for z/OS (SSMC) reside in the datasets prefixed with a server-specific dataset prefix (USR.servername), so that datasets related to one SequeLink Server can be grouped, where USR specifies the SequeLink Server environment and servername is the name of the SequeLink server.

The list of SequeLink servers that will be managed using the SSMC is maintained in the server list dataset. The name consists of the server-specific dataset prefix USR suffixed with '.SERVERS'.

Example:

A company installs SequeLink and configures three SequeLink Servers, one for the production environment and two for the test and development environment. The production server accesses DB2V8 and the testing/development servers access DB2 v8 and DB2 V9.

HLQ = SQLNK.V6R0M0 
USR1 = COMPANY.PROD 
servername1 = SQLDB2V8 
USR2 = COMPANY.DEV 
servername1 = SQLDB2V8 
servername2 = SQLDB2V9 

This results in the following datasets on your system:

SequeLink installation datasets	SQLNK.V6R0M0.CLIST SQLNK.V6R0M0.DBRM SQLNK.V6R0M0.IPE SQLNK.V6R0M0.LINKLIB SQLNK.V6R0M0.LOADLIB SQLNK.V6R0M0.MSGS SQLNK.V6R0M0.PANELS SQLNK.V6R0M0.SKELS SQLNK.V6R0M0.TABLES SQLNK.V6R0M0.SWANDM.INI SQLNK.V6R0M0.README
Serverlist datasets	COMPANY.PROD.SERVERS COMPANY.PROD.SQLDB2V8.SWANDM.INI COMPANY.PROD.SQLDB2V8.SWEVLOG COMPANY.PROD.SQLDB2V8.CNTL COMPANY.DEV.SERVERS COMPANY.DEV.SQLDB2V8.SWANDM.INI COMPANY.DEV.SQLDB2V8.SWEVLOG COMPANY.DEV.SQLDB2V8.CNTL COMPANY.DEV.SQLDB2V9.SWANDM.INI COMPANY.DEV.SQLDB2V9.SWEVLOG COMPANY.DEV.SQLDB2V9.CNTL